Resource NamingSystem/FHIR Server from package hl7.terminology#current (31 ms)

Resources that use this resource

No resources found

Resources that this resource uses

No resources found

Narrative

Note: links and images are rebased to the (stated) source

Source

{
  "resourceType" : "NamingSystem",
  "id" : "RadLex",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: NamingSystem RadLex</b></p><a name=\"RadLex\"> </a><a name=\"hcRadLex\"> </a><a name=\"RadLex-en-US\"> </a><h3>Summary</h3><table class=\"grid\"><tr><td>Defining URL</td><td>http://terminology.hl7.org/NamingSystem/RadLex</td></tr><tr><td>Version</td><td>1.0.1</td></tr><tr><td>Name</td><td>RadLex</td></tr><tr><td>Title</td><td>RadLex radiology lexicon</td></tr><tr><td>Status</td><td>active</td></tr><tr><td>Definition</td><td><div><p>RadLex is a comprehensive set of radiology terms for use in radiology reporting, decision support, data mining, data registries, education and research.</p>\n<p>RadLex Playbook is a project of the Radiological Society of North America (RSNA), and constitutes a portion of the RadLex ontology. Playbook aims to provide a standard system for naming radiology procedures, based on the elements which define an imaging exam such as modality and body part. By providing standard names and codes for radiologic studies, Playbook is intended to facilitate a variety of operational and quality improvement efforts, including workflow optimization, chargemaster management, radiation dose tracking, enterprise integration and image exchange.</p>\n<p>As of RadLex Playbook version 2.5, a four-year project to harmonize RadLex Playbook with the radiology portion of the LOINC standard has been concluded, leading to the LOINC-RSNA Radiology Playbook which is jointly managed by the Regenstrief Institute (publisher of LOINC) and RSNA. This harmonized Playbook defines a new information model for describing imaging procedures, and identifies correspondences between RadLex Playbook codes and LOINC codes. (See https://loinc.org/download/loinc-users-guide and http://pubs.rsna.org/doi/pdf/10.1148/rg.2017160188 for details.) Note that RadLex Playbook codes start with &quot;RPID&quot; followed by a numerical value. LOINC codes consist of a numerical code, followed by a hyphen and a single additional digit (called the check digit). Note that in the future, new codes will be created in the LOINC format only, not the RPID format. New adopters are encouraged to use LOINC-format codes.</p>\n<p>LOINC-format codes may be accessed at http://search.loinc.org. New code requests may be submitted to the joint Regenstrief-RSNA governance committee at https://loinc.org/submissions/.</p>\n<p>From the RSNA website:</p>\n<p>&quot;We (RSNA) recognize the benefits that come from radiologists using common language to communicate diagnostic results. For this reason, RSNA produced RadLex®, a comprehensive set of radiology terms for use in radiology reporting, decision support, data mining, data registries, education and research.</p>\n<p>RadLex provides the foundation for vital data resources used in radiology:</p>\n<ul>\n<li>The LOINC/RSNA Radiology Playbook (http://playbook.radlex.org/playbook/SearchRadlexAction)</li>\n<li>RadElement Common Data Elements (http://www.radelement.org/)</li>\n<li>RadReport Radiology Reporting Templates (http://radreport.org/)</li>\n</ul>\n<p>The development of RadLex has been supported by the National Institute of Biomedical Imaging and Bioengineering (NIBIB) and the cancer Biomedical Informatics Grid (caBIG) project.;&quot;</p>\n</div></td></tr><tr><td>Publisher</td><td>RSNA (Radiological Society of North America)</td></tr></table><h3>Identifiers</h3><table class=\"grid\"><tr><td><b>Type</b></td><td><b>Value</b></td><td><b>Preferred</b></td><td><b>Period</b></td><td><b>Comment</b></td></tr><tr><td>OID</td><td>2.16.840.1.113883.6.256</td><td>true</td><td></td><td/></tr><tr><td>URI</td><td>http://radlex.org</td><td>true</td><td>2019-05-05 --&gt; (ongoing)</td><td>This is the URL as specified by the terminology owner, and is considered authoritative.</td></tr></table></div>"
  },
  "url" : "http://terminology.hl7.org/NamingSystem/RadLex",
  "version" : "1.0.1",
  "name" : "RadLex",
  "title" : "RadLex radiology lexicon",
  "status" : "active",
  "kind" : "codesystem",
  "date" : "2022-03-31T00:00:00-00:00",
  "publisher" : "RSNA (Radiological Society of North America)",
  "contact" : [
    {
      "name" : "RSNA (Radiological Society of North America); 820 Jorie Blvd., Suite 200, Oak Brook, IL 60523-2251 USA",
      "telecom" : [
        {
          "system" : "email",
          "value" : "informatics@rsna.org"
        },
        {
          "system" : "url",
          "value" : "https://www.rsna.org/"
        },
        {
          "system" : "phone",
          "value" : "1-800-381-6660"
        }
      ]
    }
  ],
  "responsible" : "RSNA (Radiological Society of North America)",
  "description" : "RadLex is a comprehensive set of radiology terms for use in radiology reporting, decision support, data mining, data registries, education and research.\r\n\r\nRadLex Playbook is a project of the Radiological Society of North America (RSNA), and constitutes a portion of the RadLex ontology. Playbook aims to provide a standard system for naming radiology procedures, based on the elements which define an imaging exam such as modality and body part. By providing standard names and codes for radiologic studies, Playbook is intended to facilitate a variety of operational and quality improvement efforts, including workflow optimization, chargemaster management, radiation dose tracking, enterprise integration and image exchange.\r\n\r\nAs of RadLex Playbook version 2.5, a four-year project to harmonize RadLex Playbook with the radiology portion of the LOINC standard has been concluded, leading to the LOINC-RSNA Radiology Playbook which is jointly managed by the Regenstrief Institute (publisher of LOINC) and RSNA. This harmonized Playbook defines a new information model for describing imaging procedures, and identifies correspondences between RadLex Playbook codes and LOINC codes. (See https://loinc.org/download/loinc-users-guide and http://pubs.rsna.org/doi/pdf/10.1148/rg.2017160188 for details.) Note that RadLex Playbook codes start with \"RPID\" followed by a numerical value. LOINC codes consist of a numerical code, followed by a hyphen and a single additional digit (called the check digit). Note that in the future, new codes will be created in the LOINC format only, not the RPID format. New adopters are encouraged to use LOINC-format codes.\r\n\r\nLOINC-format codes may be accessed at http://search.loinc.org. New code requests may be submitted to the joint Regenstrief-RSNA governance committee at https://loinc.org/submissions/. \r\n\r\nFrom the RSNA website:\r\n\r\n\"We (RSNA) recognize the benefits that come from radiologists using common language to communicate diagnostic results. For this reason, RSNA produced RadLex®, a comprehensive set of radiology terms for use in radiology reporting, decision support, data mining, data registries, education and research.\r\n\r\nRadLex provides the foundation for vital data resources used in radiology:\r\n\r\n *  The LOINC/RSNA Radiology Playbook (http://playbook.radlex.org/playbook/SearchRadlexAction) \r\n *  RadElement Common Data Elements (http://www.radelement.org/) \r\n *  RadReport Radiology Reporting Templates (http://radreport.org/) \r\n\r\nThe development of RadLex has been supported by the National Institute of Biomedical Imaging and Bioengineering (NIBIB) and the cancer Biomedical Informatics Grid (caBIG) project.;\"",
  "uniqueId" : [
    {
      "type" : "oid",
      "value" : "2.16.840.1.113883.6.256",
      "preferred" : true
    },
    {
      "type" : "uri",
      "value" : "http://radlex.org",
      "preferred" : true,
      "comment" : "This is the URL as specified by the terminology owner, and is considered authoritative.",
      "period" : {
        "start" : "2019-05-05"
      }
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.